Repository navigation
docs(node): drop the dead sei-chain link from the Giga SS guide - #104
Conversation
The Giga SS Store migration guide opened with a callout that called docs/migration/giga_store_migration.md in sei-chain the canonical procedure and asked readers to report drift there. sei-chain removed that file, along with its other migration guides, in sei-protocol/sei-chain#4615, because operator documentation lives on docs.sei.io. The link has returned 404 in every weekly external link check since October 26. Remove the callout. This page is now where the guide is maintained, so there is no upstream copy to point readers at. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
PR SummaryLow Risk Overview No migration steps or warnings change—only the stale external provenance note is dropped. Reviewed by Cursor Bugbot for commit 5b9abe7. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
This PR deletes a stale <Info> callout that links to a sei-chain migration file. That file no longer exists. The change is small, correct, and matches the PR's reasoning, and the surrounding MDX still renders cleanly. The only notes are about process: the Codex and Cursor passes and the repository review guidelines were all empty.
Findings: 0 blocking | 4 non-blocking | 0 posted inline
Blockers
- None at the file/PR level.
Non-blocking
- The OpenAI Codex second-opinion pass produced no output (
codex-review.mdwas empty). - The Cursor second-opinion pass produced no output (
cursor-review.mdwas empty). REVIEW_GUIDELINES.mdwas empty, so this review used onlyAGENTS.mdconventions.llms-full.txtstill contains the removed callout. That's fine:AGENTS.mdsays it's generated and must not be hand-edited. Consider triggeringregenerate-llms.ymlviaworkflow_dispatchso the dead link doesn't sit in the LLM-facing file until the next weekly run.
Resolves every open broken-external-links report: #99, #100, and #102. All three flag the same link in
node/giga-storage-migration.mdx(line 23).What is the purpose of the change?
Delete a stale callout that points to a file sei-chain has removed, and close out the tracking issues.
Describe the changes to the documentation
Removed the
<Info>callout at the top of the Giga SS Store migration guide. It calleddocs/migration/giga_store_migration.mdin sei-chain the canonical procedure and asked readers to report drift there. That file no longer exists:evm-ss-splitanymore.github.com/.../blob/main/...link and itsraw.githubusercontent.comform return 404. The reports show the raw URL becauselychee.tomlremaps blob links to the raw CDN.This page is now where the guide is maintained, so there's no upstream copy to link to. I didn't pin the link to the last commit that had the file, because that would send operators to a copy sei-chain retired as stale. No other page carries a provenance callout like this one.
Notes
seidb_migration.md,seidb_archive_migration.md,seiv2_config_migration.md,evm_jsonrpc_unsupported.md).0.24.2(the versionlycheeverse/lychee-action@v2installs) with the repo'slychee.toml, over every tracked.md/.mdxfile outsidecosmos-sdk/, reports 0 errors across 1,332 links (646 unique). Vale andtyposreport no errors on the page.llms-full.txtstill contains the old callout. PerAGENTS.mdit's generated, not hand-edited, so the weeklyregenerate-llms.ymlrun will pick this up.Closes #99
Closes #100
Closes #102